feat(evalhub): make EvalHub a cluster-scoped singleton deployed in operator namespace#655
Conversation
…erator namespace Phase 1 of the multitenancy design. EvalHub is now a cluster-scoped CRD with singleton enforcement (name must be 'evalhub'), and all namespace-scoped resources (Deployment, Service, ConfigMaps, Route, ServiceAccounts, Roles, RoleBindings) are deployed in the operator namespace via a new targetNamespace() helper. - Add +kubebuilder:resource:scope=Cluster and XValidation markers - Add targetNamespace() returning r.Namespace for all sub-resources - Replace all instance.Namespace references with r.targetNamespace() - Update generateAuthReviewerClusterRoleBindingName to take explicit namespace parameter - Update sample CR: remove namespace, rename to 'evalhub' - Update unit and integration tests for cluster-scoped CR
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Phase 1 of the multitenancy design. EvalHub is now a cluster-scoped CRD with singleton enforcement (name must be 'evalhub'), and all namespace-scoped resources (Deployment, Service, ConfigMaps, Route, ServiceAccounts, Roles, RoleBindings) are deployed in the operator namespace via a new targetNamespace() helper.